Skip to content

Update gorilla/websocket to v1.5.3 - #160

Open
ai-collaboration-app[bot] wants to merge 1 commit into
mainfrom
cve-gorilla-websocket-1.5.3
Open

Update gorilla/websocket to v1.5.3#160
ai-collaboration-app[bot] wants to merge 1 commit into
mainfrom
cve-gorilla-websocket-1.5.3

Conversation

@ai-collaboration-app

@ai-collaboration-app ai-collaboration-app Bot commented Aug 25, 2026

Copy link
Copy Markdown

Clears GHSA-w67g-5rqw-f597 (medium) from the published stackstate-cli2 images: gorilla/websocket below v1.5.3 masks WebSocket frames with a key from math/rand. It is linked via k8s.io/client-go's transport/websocket and tools/remotecommand, so the exec path reaches it.

Indirect-only bump; the go directive is untouched, so release builds keep the go1.25.13 toolchain from #159.

Ticket: https://github.com/StackVista/cve-reporter/issues/32
Finding revision: sha256:aab70beb56814ac92a62d46ece1369f828e32e9735ae21d0288a0268751fa69f (cycle 32956756631; first raised as sha256:584c08ac…)

Validated on a representative image built from this branch with docker/Dockerfile.goreleaser, revalidated 2026-08-26 on current scanner DBs: go test ./... all green on go1.25.13, sts version runs, binary reports gorilla/websocket v1.5.3, Grype 0.117.0 0 matches, Trivy 0.74.0 vulnerability 0 critical/high/medium/low, Trivy secret 0.

Reviewer note — this will not clear the ticket's remaining high on its own. That row (CVE-2026-46600 on stdlib go1.25.13) is a scanner-data artifact: image-pipeline's scan-image action pins GRYPE_VERSION: 0.112.0, and Grype 0.117.0 on a 2026-08-25 DB reports it on neither published digest. The upstream range starts at 1.26.0, so 1.25.x was never affected. It needs the Grype pin bumped in image-pipeline, not a change here. Do not move the CLI to Go 1.26.x for it — 1.25.13 has no known stdlib advisories today, while 1.26.5 has eight.

The distroless-debian11 base also carries five tzdata DLAs at UNKNOWN severity. They predate this branch and sit outside the scan gate; not in scope here.

GHSA-w67g-5rqw-f597: versions below v1.5.3 derive the WebSocket frame
mask key from math/rand rather than a cryptographic source. The CLI
links it through k8s.io/client-go's transport/websocket and
tools/remotecommand, so it is reachable from the exec path.

The dependency stays indirect and the Go directive is unchanged, so
release builds keep the go1.25.13 toolchain pinned by #159.

Ticket: StackVista/cve-reporter#32
Finding revision: sha256:584c08ac7ac36342068919d81349c67b61457518511df9a00b23644728294094

Co-authored-by: Cve Ticket Reconciler <cve-ticket-reconciler@stackstate.invalid>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant